Review Documentation: Familiarize yourself with the EFS SFTP transition requirements and any documentation Katherine may have sent regarding the setup and fuel file download tool.
Gather Credentials: Ensure you have the new SFTP credentials, including:
Access Funded Vendor Controls: Go to the LoadMaster server in the dev environment and navigate to the Communications tab under Funded Vendor Controls.
Apply New SFTP Credentials:
Run Initial Connection Test: Open WinSCP or any SFTP client that allows external communication testing.
Verify Internal & External Connection: Test that the connection works both from inside the server and externally, confirming no issues with IP blocks or access restrictions.
Modify Control Files: Update funded vendor control files to reference the new SFTP URL.
Download Fuel Transaction Files: Initiate a download of the fuel transaction files using the configured fuel file download tool. Ensure the download completes successfully and that files are accessible in the expected location.
Check Carrier ID: Ensure that the carrier ID 55731285 is whitelisted in both dev and production environments.
Check Batch C Codes in Checks Tab: Confirm that the relevant batch C codes are set up correctly. Adjust if necessary to avoid disruptions during production testing.
Record Successful Tests: Log each successful connection, download, and configuration test to ensure traceability.
Note Any Issues: Document any issues encountered with the connection, whitelisting, or file access for further troubleshooting.
Coordinate Change Request for Production: Once all tests are successfully completed in the dev environment, initiate a Change Request for implementing the changes in production.
Confirm December 2 Deadline: Ensure that all testing and configuration adjustments are completed before the target deadline for the decommissioning of the FTP servers.
McLeod Support: If additional troubleshooting or guidance is needed, Katherine has offered support for screen sharing and connection testing.
WinSCP Documentation: Refer to WinSCP resources if specific troubleshooting with external communication tests is required.
